APS updates #2528
APS updates #2528
Conversation
djmitche
force-pushed
the
aps-updates
branch
from
ac2c766 to
31003d5
Compare
| @@ -8,6 +8,10 @@ Before we can start running Rust code, we need to do some initialisation. | |||
|
|
|||
| <details> | |||
|
|
|||
| This code is in `src/bare-metal/aps/examples/entry.S`. It's not necessary to | |||
| understand this in detail -- the takeaway is that typically some low-level setup | |||
| is needed to meet Rust's expectations of the system. | |||
There was a problem hiding this comment.
When I'm teaching I usually walk through the initialisation here, and talk about why cache coherency issues are a problem, because that is a common mistake I've seen. If people are used to doing similar things in C then it's pretty much the same, but if they're not then I think it's important to understand.
There was a problem hiding this comment.
I might have a hard time doing that! For a student not familiar with assembly (or at least ARM assembly), what is the takeaway lesson here?
Is the cache coherency problem the one mentioned elsewhere in the speaker notes, where a VM not using an MMU might have coherency issues with a host that is using the MMU?
There was a problem hiding this comment.
Happy New Year folks!
cache coherency issues are a problem
Okay, I don't think I did that in my last class, sorry! I think it would be good to expand the slides/notes with this material as well if it's important.
Cc @hurryabit.
|
The CI failures here are I will rebase in hopes that fixes it.. |
djmitche
force-pushed
the
aps-updates
branch
2 times, most recently
from
4e14437 to
23fd0e6
Compare
These are some minor updates from walking through the session myself. * Add some context to the `entry.S` slide, which is otherwise a bit terrifying for someone who does not speak ARM assembly. * Include a simple, fake example of MMIO. * Add a "Using It" section to the minimal UART segment, parallel to the better UART * Better explanation of the `unwrap` calls in the logging example. Unwrap is never "unsafe", so remove that word. * Allow dead code in some `.rs` files. * Remove redundant warning about use of memory before MMU setup. * Rephase text about buddy-system * Fix lint warning in spin slide.
These are some minor updates from walking through the session myself.
entry.Sslide, which is otherwise a bit terrifying for someone who does not speak ARM assembly.unwrapcalls in the logging example. Unwrap is never "unsafe", so remove that word..rsfiles.